Method and apparatus for completing pending write requests to volatile memory prior to transitioning to self-refresh mode

ABSTRACT

In one embodiment, an apparatus comprises a processor core and a power control unit. The power control unit is to identify the occurrence of a power loss from a primary power source, instruct the I/O controller to block further write requests from the one or more I/O devices and to send at least one pending write request stored by the I/O controller to the memory controller, and instruct the memory controller to complete at least one pending write request stored by the memory controller and to cause the memory to be placed into a self-refresh mode.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/816,445, filed on Aug. 3, 2015, and entitled METHOD AND APPARATUS FORCOMPLETING PENDING WRITE REQUESTS TO VOLATILE MEMORY PRIOR TOTRANSITIONING TO SELF-REFRESH MODE. The disclosure of the priorapplication is considered part of and is hereby incorporated byreference in its entirety in the disclosure of this application.

FIELD

The present disclosure relates in general to the field of computerdevelopment, and more specifically, to completing pending write requeststo volatile memory prior to transitioning to self-refresh mode.

BACKGROUND

A computer system may include one or more central processing units(CPUs). A CPU may include an integrated memory controller and/or anintegrated input/output (I/O) controller. Such an integratedimplementation may sometimes be referred to as a System On a Chip (SOC).A CPU may also be coupled to an external I/O controller (i.e., an I/Ocontroller that is not on the same die or package as the CPU) via a busor other interconnect. A system memory coupled to the CPU may store datautilized by a CPU and/or I/O devices of the computer system. As oneexample, data stored in the system memory may be consumed by a CPUand/or an I/O device.

A computer system operates using power received from one or more primarypower sources such as a battery or electrical outlet. The computersystem may experience a power loss in which the computer system ceasesto receive power from its primary power source(s). A computer system mayinclude one or more battery backup units to provide limited batterypower to some of the components (e.g., the system memory) during thepower loss.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of components of a computer system inaccordance with certain embodiments.

FIG. 2 illustrates a block diagram of components for completing pendingwrite requests and putting memory into self-refresh mode in accordancewith certain embodiments.

FIG. 3 illustrates a signal flow diagram illustrating examplecommunications between components of FIG. 2 in accordance with certainembodiments.

FIG. 4 illustrates a method for completing pending write requests andputting memory into self-refresh mode in accordance with certainembodiments.

FIG. 5 illustrates a method for blocking incoming write requests duringpower loss in accordance with certain embodiments.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Although the drawings depict particular computer systems, the conceptsof various embodiments are applicable to any suitable integratedcircuits and other logic devices. Examples of devices in which teachingsof the present disclosure may be used include desktop computer systems,server computer systems, storage systems, handheld devices, tablets,other thin notebooks, systems on a chip (SOC) devices, and embeddedapplications. Some examples of handheld devices include cellular phones,Internet protocol devices, digital cameras, personal digital assistants(PDAs), and handheld PCs. Embedded applications may include amicrocontroller, a digital signal processor (DSP), a system on a chip,network computers (NetPC), set-top boxes, network hubs, wide areanetwork (WAN) switches, or any other system that can perform thefunctions and operations taught below.

FIG. 1 illustrates a block diagram of components of a computer system100 in accordance with certain embodiments. System 100 includes acentral processing unit (CPU) 104 coupled to a system memory 106 and oneor more I/O devices 108. The CPU is also coupled to one or more otherI/O devices 112 through external I/O controller 110. During operation,data may be transferred between I/O devices 108 and 112 and the CPU 104.In at least some instances, this data may be stored in system memory 106before a core or other processing element of the CPU accesses the data.System memory 106 may include volatile memory that requires periodicrefreshing in order to maintain data stored therein.

During normal operation, the components of system 100 receive power froma power subsystem that may be coupled to one or more primary powersupply sources such as line power, one or more batteries, and/or anUninterruptible Power Source (UPS). System 100 may experience a powerloss in which the system ceases to receive power from its primary powersupply source(s). For example, in a system having line power as itsprimary power supply source, a power loss may occur when an electricaloutlet ceases to provide power to the system (e.g., because the outletloses a connection to power or because a power cord that couples thesystem to the outlet is unplugged from the system or outlet). As anotherexample, in a system with a battery acting as a primary power supplysource, a power loss may occur when the battery ceases to provide powerto the system (e.g., the battery does not contain sufficient charge oris detached from the system). In a system having multiple primary powersupply sources (e.g., a battery and an electrical outlet), a power lossmay occur when none of the primary power supply sources are able toprovide power to the system following a period of time when at least oneof the primary power supply sources provided power to the system.

In some situations, a power loss may occur during the writing of datareceived from I/O devices 108 or integrated I/O devices on CPU 104 tothe system memory 106. Some applications require the contents of thesystem memory 106 to be preserved during power loss. In someembodiments, this may be accomplished by coupling the system memory 106to a backup power source and placing the system memory 106 in aself-refresh mode, where the data stored in system memory 106 isrefreshed periodically. In embodiments where the system memory 106comprises dynamic random-access memory (DRAM), the process oftransitioning the system memory 106 to self-refresh mode may be referredto as Asynchronous DRAM Refresh (ADR).

In addition to maintaining the contents of the system memory 106 duringpower losses, certain applications require that writes targeting systemmemory 106 are performed in accordance with ordering rules, since awrite to system memory 106 from an I/O interface of the CPU can reachthe system memory out of order. Thus, in order to avoid problemsassociated with out of order writes, system 100 may ensure that allwrites accepted by CPU 104 are committed to system memory 106, even inthe event of a power loss.

Particular systems may utilize software executed by one or more cores ofCPU 104 to implement this functionality upon reception of an interruptsupplied in response to a power loss indication. For example, a systemmanagement interrupt (SMI) handler could be used to block future writesfrom the I/O devices and drain the accepted writes to system memoryprior to putting the system memory into self-refresh mode. However, suchan implementation may require a relatively large backup power source inorder to power the entire platform (including one or more cores of a CPUand external I/O controller logic) until the SMI handler completesexecution. Moreover, utilization of an SMI handler may require aplatform implementer to develop and validate customized software basedon the particular implementation of the platform and to predict theamount of power required to execute the software successfully. Moreover,in such a system, there may not be an option to send an indication thatthe system memory has been placed in self-refresh to logic controllingthe backup power source, thus forcing reliance on a timer-basedmechanism for activating the provision of power to the system memory bythe backup power source.

Various embodiments of the present disclosure include a hardware basedflow for completing pending write requests and putting the system memory106 into self-refresh mode during a power loss. A power control unit(PCU) of CPU 104 may coordinate the quiescence of inbound write data tofacilitate the preservation of data in system memory 106 withoutviolating write ordering for inbound writes generated by I/O devices 108and integrated I/O devices. Various embodiments do not utilize an SMIhandler and instructions executed by a core to implement steps of theADR sequence. Particular embodiments provide various technicaladvantages, including faster completion of the ADR sequence and reducedpower usage (thus decreasing the size of a power source such as abattery used to provide backup power to system 100 during the ADRsequence).

FIG. 2 illustrates a block diagram of a system 200 for completingpending write requests and putting system memory 106 into self-refreshmode in accordance with certain embodiments. In addition to aspectsdescribed below, system 200 may include any suitable characteristicsdescribed above with respect to system 100.

In the depicted embodiment, system 200 includes CPU 104 which is coupledto system memory 106, I/O devices 108, external I/O controller 110, andcomplex programmable logic device (CPLD) 114. Additional I/O devices 112may be coupled to CPU 104 through external I/O controller 110. System200 also includes a battery backup unit (BBU) 116 that may providebackup power to system memory 106 in response to a command received fromCPLD 114.

CPU 104 includes cores 118, power control unit (PCU) 120, I/O controller122, and memory controller 124. Each of the I/O controller 122 and thememory controller 124 may include a write buffer 126 and 132 that may beused to store write commands received from I/O devices 108 and/orintegrated I/O devices 130 that have been accepted by the I/O controller122, but not yet written to system memory 106. I/O controller 122 mayfurther include root ports 128. Each of these components is described inmore detail below.

In some embodiments, all or some of the elements of system 200 areresident on (or coupled to) the same circuit board (e.g., amotherboard). In particular embodiments, one or more of the I/O devices108 or 112 are located off of the circuit board and may be coupled toone or more ports of the circuit board. In various embodiments, anysuitable partitioning between blocks may exist. For example, theelements depicted in CPU 104 may be located on a single die or packageor any of the elements of CPU 104 may be located off-chip. As anotherexample, the CPLD may be located within (e.g., on the same board, die,or package as) external I/O controller 110.

The elements of system 200 may be coupled together in any suitablemanner. For example, a bus may couple any of the components together. Abus may include any known interconnect, such as a multi-drop bus, a meshinterconnect, a ring interconnect, a point-to-point interconnect, aserial interconnect, a parallel bus, a coherent (e.g. cache coherent)bus, a layered protocol architecture, a differential bus, and a Gunningtransceiver logic (GTL) bus. In various embodiments an integrated I/Osubsystem includes point-to-point multiplexing logic between variouscomponents of system 200, such as cores 118, one or more memorycontrollers 124, root ports 128, integrated I/O devices 130, directmemory access (DMA) logic (not shown), etc.

CPU 104 may comprise any processor or processing device, such as amicroprocessor, an embedded processor, a digital signal processor (DSP),a network processor, a handheld processor, an application processor, aco-processor, a system on a chip (SOC), or other device to execute code.CPU 104, in the depicted embodiment, includes two processing elements(cores 118A and 118B in the depicted embodiment), which may includeasymmetric processing elements or symmetric processing elements.However, CPU 104 may include any number of processing elements that maybe symmetric or asymmetric.

In one embodiment, a processing element refers to hardware or logic tosupport a software thread. Examples of hardware processing elementsinclude: a thread unit, a thread slot, a thread, a process unit, acontext, a context unit, a logical processor, a hardware thread, a core,and/or any other element, which is capable of holding a state for aprocessor, such as an execution state or architectural state. In otherwords, a processing element, in one embodiment, refers to any hardwarecapable of being independently associated with code, such as a softwarethread, operating system, application, or other code. A physicalprocessor (or processor socket) typically refers to an integratedcircuit, which potentially includes any number of other processingelements, such as cores or hardware threads.

A core may refer to logic located on an integrated circuit capable ofmaintaining an independent architectural state, wherein eachindependently maintained architectural state is associated with at leastsome dedicated execution resources. A hardware thread may refer to anylogic located on an integrated circuit capable of maintaining anindependent architectural state, wherein the independently maintainedarchitectural states share access to execution resources. As can beseen, when certain resources are shared and others are dedicated to anarchitectural state, the line between the nomenclature of a hardwarethread and core overlaps. Yet often, a core and a hardware thread areviewed by an operating system as individual logical processors, wherethe operating system is able to individually schedule operations on eachlogical processor.

Physical CPU 104, as illustrated in FIG. 2, includes two cores—core 118Aand 118B. Here, cores 118 may be considered symmetric cores. In anotherembodiment, core 118A includes an out-of-order processor core, whilecore 118B includes an in-order processor core. However, cores 118A and118B may be individually selected from any type of core, such as anative core, a software managed core, a core adapted to execute a nativeInstruction Set Architecture (ISA), a core adapted to execute atranslated ISA, a co-designed core, or other known core. In aheterogeneous core environment (i.e. asymmetric cores), some form oftranslation, such as binary translation, may be utilized to schedule orexecute code on one or both cores.

Core 118A may include a decode module coupled to a fetch unit to decodefetched elements. Fetch logic, in one embodiment, includes individualsequencers associated with thread slots of cores 118. Usually a core 118is associated with a first ISA, which defines/specifies instructionsexecutable on core 118. Often machine code instructions that are part ofthe first ISA include a portion of the instruction (referred to as anopcode), which references/specifies an instruction or operation to beperformed. The decode logic may include circuitry that recognizes theseinstructions from their opcodes and passes the decoded instructions onin the pipeline for processing as defined by the first ISA. For example,as decoders may, in one embodiment, include logic designed or adapted torecognize specific instructions, such as transactional instructions. Asa result of the recognition by the decoders, the architecture of core118 takes specific, predefined actions to perform tasks associated withthe appropriate instruction. It is important to note that any of thetasks, blocks, operations, and methods described herein may be performedin response to a single or multiple instructions; some of which may benew or old instructions. Decoders of cores 118A and 118B, in oneembodiment, recognize the same ISA (or a subset thereof). Alternatively,in a heterogeneous core environment, decoders of cores 118A and 118Brecognize a second ISA (either a subset of the first ISA or a distinctISA).

In various embodiments, cores 118 may also include one or morearithmetic logic units (ALUs), floating point units (FPUs), caches,instruction pipelines, interrupt handling hardware, registers, or otherhardware to facilitate the operations of the cores 118.

System memory 106 may store data that is used by cores 118 to performthe functionality of computer system 200. For example, data associatedwith programs that are executed or files accessed by cores 118 may bestored in system memory 106. Thus, system memory 106 may store dataand/or sequences of instructions that are executed by the cores 118.System memory 106 may be dedicated to CPU 104 or shared with otherdevices of computer system 200.

System memory 106 may include volatile memory. Volatile memory is astorage medium that requires power to maintain the state of data storedby the medium. Examples of volatile memory may include various types ofrandom access memory (RAM), such as dynamic random access memory (DRAM)or static random access memory (SRAM). One particular type of DRAM thatmay be used in system memory is synchronous dynamic random access memory(SDRAM). In particular embodiments, DRAM of system memory 106 complieswith a standard promulgated by the Joint Electron Device EngineeringCouncil (JEDEC), such as JESD79F for Double Data Rate (DDR) SDRAM,JESD79-2F for DDR2 SDRAM, JESD79-3F for DDR3 SDRAM, or JESD79-4A forDDR4 SDRAM (these standards are available at www.jedec.org). In someembodiments, system memory 106 comprises one or more memory modules,such as dual in-line memory modules (DIMMs). System memory 106 maycomprise any suitable type of memory and is not limited to a particularspeed or technology of memory in various embodiments.

In various embodiments, system memory 106 comprises DRAM that storesdata in cells that each include a capacitor. The data stored by aparticular cell is dependent on the amount of charge stored by the cell.The capacitors in the cells of the DRAM will slowly discharge throughtransistors in the DRAM. The information stored by the capacitors willeventually be lost unless the capacitor charge is periodicallyrefreshed. In some embodiments, a refresh operation may involverestoring the charge on the capacitors of a given row of the DRAMthrough row activation. In a self-refresh mode, system memory 106 mayperiodically refresh each of its cells such that it retains the state ofdata stored therein. In various embodiments, in self-refresh mode, thesystem memory 106 may retain its data without external clocking (e.g.,from memory controller 124) and may utilize an internal timer inconjunction with the refreshing of its cells.

In some embodiments, the implementation of a self-refresh mode by systemmemory 106 allows data in the memory to be maintained using power from abackup power source, such as a battery backup unit when a power lossoccurs. The system memory 106 may be used to store any suitable data,including data that should be preserved, even in the event of a powerloss, such as cache configuration data, network data, redundant array ofindependent disk (RAID) transactions, and/or data associated with otherpending transactions. In some embodiments, such data is received throughthe I/O controller 122 from I/O devices 108 or integrated I/O devices130.

Memory controller 124 is an integrated memory controller that includeslogic (e.g., hardware and/or software) to control the flow of data goingto and from the system memory 106. Memory controller 124 may includelogic necessary to read from and write to system memory 106 and to causerefreshing of the values stored in system memory 106. During operation,memory controller may select one or more addresses (e.g., row and/orcolumn addresses) of the system memory 106 to read from or write to.Memory controller 124 may receive write requests from cores 118 and I/Ocontroller 122 and may provide data specified in these requests tosystem memory 106 for storage therein. In the embodiment depicted,memory controller 124 includes write buffer 132. Write buffer 132 maystore pending write requests received from an I/O device 108 or 112 thathas been accepted by the memory controller 124 but has not yet beenwritten to system memory 106. Memory controller 124 may also read datafrom system memory 106 and provide the read data to I/O controller 122or a core 118.

I/O devices 108 may include any suitable devices capable of transferringdata to and receiving data from an electronic system, such as CPU 104.For example, an I/O device 108 may be an audio/video (A/V) devicecontroller such as a graphics accelerator or audio controller; a datastorage device controller, such as a flash memory device, magneticstorage disk, or optical storage disk controller; a wirelesstransceiver; a network processor; a network interface controller; or acontroller for another input devices such as a monitor, printer, mouse,keyboard, or scanner; or other suitable device. In various embodiments,the I/O device 108 may be coupled to CPU 104 and may send data to CPU104 and receive data from CPU 104. An I/O device 108 may communicatewith the I/O controller 122 of the CPU 104 using any suitable signalingprotocol, such as peripheral component interconnect (PCI), PCI Express(PCIe), Universal Serial Bus (USB), Serial Attached SCSI (SAS), SerialATA (SATA), Fibre Channel (FC), IEEE 802.3, IEEE 802.11, or othercurrent or future signaling protocol. In the embodiment depicted, I/Odevices 108 are located off-chip (i.e., not on the same chip as CPU104).

I/O controller 122 is an integrated I/O controller that includes logic(e.g., hardware and/or software) for communicating data between CPU 104and I/O devices 108 and integrated I/O devices 130. Similar to memorycontroller 124, I/O controller 122 may also include a write buffer 126to store pending write requests received from an I/O device 108 orintegrated I/O device 130 accepted by the I/O controller 122 but not yetpassed on to memory controller 124. In the embodiment depicted, I/Ocontroller includes root ports 128 and integrated I/O devices 130.

A root port 128 may couple one or more I/O devices 108 to memorycontroller 124 and/or a core 118. In various embodiments, a root portmay be located in a root complex. For example, the root complex mayinclude an upstream root port and one or more downstream root ports. Inparticular embodiments, an upstream root port 128 may be coupled tomemory controller 124 and/or a core 118 and a downstream root port maycouple to an I/O device 108, an integrated I/O devices 130, a switch(which may couple multiple I/O devices 108 or integrated I/O devices toa root port 128), or a bridge that may couple to one or more I/O devices108 or integrated I/O devices that use a signaling protocol that isdifferent from the protocol used by the root port 128 (e.g., a PCIebridge to PCI, PCI-X, USB, or other protocol).

I/O controller 122 may also comprise one or more integrated I/O devices130. An integrated I/O device 130 may have any of the characteristicslisted above with respect to I/O devices 108, but is integrated on thesame chip as the rest of the CPU.

In various embodiments, a root port 128 or integrated I/O device 130 orsimilar components on external I/O controller 110 may utilize a PCIearchitecture. For example, a root port 128 may be a PCIe root portand/or an integrated I/O device 130 may be a PCIe endpoint. A primarygoal of PCIe is to enable components and devices from different vendorsto inter-operate in an open architecture, spanning multiple marketsegments; clients (desktops and mobile), servers (standard andenterprise), and embedded and communication devices. PCIe is a highperformance, general purpose I/O interconnect defined for a wide varietyof future computing and communication platforms. Any suitable PCIeprotocol may be used in various embodiments, such as PCIe 1.0a, 1.1,2.0, 2.1, 3.0, 3.1, or future PCIe protocol (specifications for theseprotocols are available at www.pcisig.com). Some PCI attributes, such asits usage model, load-store architecture, and software interfaces, havebeen maintained through its revisions, whereas previous parallel busimplementations have been replaced by a highly scalable, fully serialinterface. The more recent versions of PCIe take advantage of advancesin point-to-point interconnects, switch-based technology, and packetizedprotocol to deliver new levels of performance and features. Powermanagement, quality of service (QoS), hot-plug/hot-swap support, dataintegrity, and error handling are among some of the advanced featuressupported by PCIe. Although various embodiments may include PCIe rootports and endpoints, in other embodiments root port 128 and/orintegrated I/O device 130 may utilize any suitable communicationprotocol.

Power control unit 120 may include any suitable logic (hardware and/orsoftware) to receive an indication of a power loss, cause the blockingof future write requests from I/O devices 108 and/or integrated I/Odevices 130, cause the flushing of pending write requests to systemmemory 106, and cause system memory 106 to go into self-refresh. Powercontrol unit 120 may also provide logic for providing a signalindicating that the system memory 106 has been instructed to move to theself-refresh mode. For example, the signal may be provided to logic(e.g., CPLD 114) operable to cause BBU 116 to provide backup power tosystem memory 106. In some embodiments, PCU 120 may include sensors fortemperature, current, and/or voltage and may optimize voltages and/orclock frequencies used by cores 118.

In various embodiments, PCU may comprise a state machine that may directthe sending of commands operable to perform the features cited above andto transition in response to signals received from other components ofsystem 200, such as CPLD 114, memory controller 124, and/or I/Ocontroller 122. In one embodiments, PCU comprises a microcontroller thatexecutes embedded firmware to perform the operations described herein.In one embodiment, PCU 120 performs some or all of the PCU functionsdescribed herein using hardware without executing software instructions.For example, PCU 120 may include fixed and/or programmable logic toperform the functions of the PCU.

PCU 120 may be a component that is discrete from the cores 118A and118B. In particular embodiments, the PCU 120 runs at a clock frequencythat is different from the clock frequencies used by core 118A and 118B.In some embodiments where PCU is a microcontroller, PCU 120 executesinstructions according to an ISA that is different from an ISA used bycores 118.

External I/O controller 110 may include logic (e.g., hardware and/orsoftware) to manage the flow of data between one or more CPUs 104 andI/O devices 112. In some embodiments, external I/O controller 110includes additional PCIe root ports and/or other integrated I/O devices,such as those described above with respect to CPU 104. In particularembodiments, external I/O controller 110 is located on a motherboardalong with the CPU 104. The external I/O controller 110 may exchangeinformation with components of CPU 104 using point-to-point or otherinterfaces.

CPLD 114 is a programmable logic device 114 operable to detect the onsetof a loss of one or more power supplies for CPU and/or system memory 106and to notify CPU 104 of such. The components of system 200 (e.g., CPU104, external I/O controller 110, and/or the system memory 106) may bepowered by one or more primary power sources via one or more voltagerails (or power rails) or by a backup power source, such as a batterybackup unit. Each of the elements might be powered by a separate powerrail and/or by common power rails. In some embodiments, a component maybe powered via multiple voltage rails. A power loss in one or more ofthese power rails supplying power from a primary power source may beidentified in any suitable manner. For example, CPLD 114 or othersuitable logic may detect a drop in voltage and/or current supplied by aprimary power supply. System 200 may include power circuitry that allowsfor provision of power to particular components of system 200 for ashort duration upon power loss. For example, power circuitry of system200 may include one or more capacitors or backup batteries that maysupply power to CPU 104 (or particular components thereof) and/or systemmemory 106 to allow the completion of pending write requests to systemmemory 106 and the transition of system memory 106 to self-refresh mode,even after a power loss has occurred. In various embodiments, at least aportion of such power circuitry may be included within BBU 116 (e.g.,the power circuitry could be used to power system memory 106 when itenters self-refresh mode) while in other embodiments this powercircuitry may be separate from BBU 116. Upon detection of a power loss,CPLD 114 may send a power loss indication to PCU 120 of CPU 104. AfterPCU 120 has caused incoming write requests from I/O devices 108 and/orintegrated I/O devices to be stopped, pending write requests to thesystem memory 106 to be completed, and system memory 106 to transitionto a self-refresh mode, PCU 120 may send CPLD 114 a signal indicatingthat the ADR sequence is complete. CPLD 116 may then send a signal toBBU 116 to cause BBU to provide backup power to system memory 106 toallow system memory 106 to self-refresh. In some embodiments, backuppower is also decoupled from the CPU at this stage.

In various embodiments, the CPLD 114 performs other functions such asmonitoring whether power is available and determining whether power isstable (and may provide associated indications to other components ofsystem 200) and controlling reset signals of components of the CPU 104or other logic in system 200. Although, this disclosure describesfunctions associated with power detection and control with respect toCPLD 114, any suitable logic (fixed or programmable) may be used toprovide such functionality. Moreover, such logic may be located at anysuitable location within system 200 (such as within external I/Ocontroller 110 or on the same circuit board as the external I/Ocontroller 110 and/or CPU 104).

BBU 116 may include any suitable power source (e.g., a capacitor orbattery) and control logic that enables selectable provisioning of thepower source to system memory 106. In some embodiments battery backuppower provided by BBU 116 is provided only to system memory 106 and notto any other part of the system, such as CPU 104 or external I/Ocontroller 110. BBU 116 may include any suitable power circuitry, suchas one or more voltage regulators powered by a battery.

FIG. 3 illustrates a signal flow diagram illustrating examplecommunications between components of FIG. 2 in accordance with certainembodiments. Upon detection of a power loss, CPLD 114 sends power lossindication 302 to PCU 120. The PCU 120 then sends disable request 304 tothe I/O controller 122 to block additional write requests from I/Odevices 108 and/or integrated I/O devices 130. For example, links to theroot ports 128 and integrated I/O devices 130 may be disabled inresponse to the requests 304. One or more disable confirmations 306 maybe received from the root ports 128 and integrated I/O devices 130 viathe I/O controller 122, verifying that incoming write requests are nowbeing blocked. In one embodiment, PCU 120 reads a register associatedwith a particular link or device to verify that the link or device hasbeen disabled.

At step 308, PCU 120 sends flush buffer request 308 to I/O controller122. In response, I/O controller 122 may transfer all pending writerequests 310 stored in write buffer 126 to the memory controller 124.The I/O controller 122 may send PCU 120 a flush buffer complete signal312 once the write requests 310 have been moved to write buffer 132 ofmemory controller 124. Alternatively, PCU 120 may wait a predeterminedperiod of time to allow the write requests to be transferred withoutreceiving a confirmation signal.

PCU 120 then sends a disable request 314 to memory controller 124 toprevent the memory controller from accepting additional write requests.Memory controller 124 sends disable confirmation 316 back to the PCU 120once it has blocked incoming requests. The PCU 120 then sends a flushbuffer request 318 to the memory controller 124 to instruct memorycontroller 124 to complete the pending write requests stored in writebuffer 132. The writes are performed in system memory 106 and then thememory controller 124 sends a flush buffer complete signal 320 to thePCU. The PCU 120 then sends a self-refresh command 322 to memorycontroller 124 to instruct the memory controller to place the systemmemory 106 into a self-refresh mode. Memory controller 124 then sends aself-refresh confirmation signal 324 to the PCU 120. In alternativeembodiments, instead of receiving confirmation signals from the memorycontroller 124, the PCU 120 may simply wait for a predetermined periodof time before sending the next communication. In yet other embodiments,communications 314, 128, and/or 322 may be combined into one or morecommunications between the PCU 120 and memory controller 124.

Upon reception of a self-refresh confirmation signal 324 (or afterwaiting a predetermined period of time), PCU 120 sends a backup sequencecomplete signal 326 to CPLD 114 which then sends a power enable signal328 to the BBU 116 which provides power to system memory 106 in responseto receiving the power enable signal.

The signals described in FIG. 3 are merely representative ofcommunications that may be sent in particular embodiments. In otherembodiments, for example, the PCU 120 may not receive one or more of theconfirmation signals verifying that the actions requested by the PCU 120have been completed. In such embodiments, PCU 120 may simply send acommand after an appropriate time has passed for the previous command tobe performed. In other embodiments, additional signals may be sent amongthe components of system 200. For example, if a confirmation signal thata particular action has been performed is not received within a certainperiod of time by the PCU 120, the PCU 120 may send an error signal tothe CPLD (or may forego the sending of the backup sequence completesignal 326). Various embodiments of the present disclosure contemplateany suitable signaling mechanisms for accomplishing the functionsdescribed herein.

FIG. 4 illustrates a method 400 for completing pending write requestsand putting system memory 106 into self-refresh mode during power lossin accordance with certain embodiments. The various steps of method 400may be performed by any suitable logic of CPU 104, such as PCU 120(although the steps below will be explained with respect to the PCU, anyother suitable logic may perform the steps).

At step 402, the occurrence of a power loss associated with CPU 104and/or system memory 106 is identified. In some embodiments, PCU 120identifies the power loss in response to a signal received by logic thatdetects the power loss (e.g., CPLD 114). In other embodiments, PCU 120itself identifies the power loss by detection of a drop in voltageand/or current of a power source.

At step 404, the I/O controller 122 is instructed to block writerequests. For example, each downstream root port 128 or integrated I/Odevice 130 may be disabled within I/O controller 122 to block furtherincoming write requests.

At step 406, the I/O controller 122 is instructed to send pending writerequests to the memory controller 124. For example, I/O controller 122may buffer write requests received from I/O devices 108 and integratedI/O devices 130 in a write buffer 126. Upon receiving a command from thePCU 120, the I/O controller 122 may send the contents of the writebuffer to the memory controller 124.

At step 408, the memory controller 124 is instructed to block writerequests, complete pending write requests, and place system memory 106into self-refresh mode. In various embodiments, PCU 120 may wait apredetermined period of time (or wait until a confirmation from the I/Ocontroller is received) to ensure that the write requests from the I/Ocontroller 122 have reached the memory controller 124 before instructingthe memory controller 124 to block incoming write requests. Afterblocking incoming write requests, memory controller 124 completes anypending write requests stored in write buffer 132 by writing thespecified data in the requests to system memory 106. Memory controller124 then causes system memory 106 to enter self-refresh mode. The memorycontroller 124 may then send a confirmation signal indicating that thememory has been placed into self-refresh mode to PCU 120. At step 410,an indication that memory has been placed in self-refresh mode isprovided. For example, PCU 120 may send the indication to logic incommunication with the BBU 116, such as CPLD 114. In response toreceiving this indication, the CPLD 114 (or other suitable logic) maycause the battery backup unit 116 to provide backup power to systemmemory 106 such that system memory 106 may periodically refresh its datawhile waiting for power to be restored within system 200. In someembodiments, the CPLD 114 (or other suitable logic) may also cause powerto the CPU 104 and external I/O controller 110 to be cut off once thesystem memory enters self-refresh (e.g., this may be performed inresponse to the indication received from the PCU 120).

Some of the steps illustrated in FIG. 4 may be repeated, combined,modified or deleted where appropriate, and additional steps may also beadded to the flowchart. Additionally, steps may be performed in anysuitable order without departing from the scope of particularembodiments.

FIG. 5 illustrates a method 500 for blocking incoming write requestsduring power loss in accordance with certain embodiments. Method 500 isone example illustrating how the I/O controller 122 may be instructed toblock write requests in a particular implementation of CPU 104 havingone or more I/O devices 108 coupled to root ports 128 and integrated I/Odevices 130 comprising DMA and Gigabit Ethernet (GbE) controllerscoupled to root ports 128 via Intel On-Chip System Fabric (IOSF) primarybridges. However, in other embodiments, any suitable methods forblocking incoming write requests may be used (e.g., writing to busmaster enable bits on the I/O devices).

At step 502, a write is performed to a link control register (e.g., alink disable bit) of each root port 128. This may cause a Link Trainingand Status State Machine (LTSSM) of the root port 128 to disable thelink between the root port and one or more I/O devices 108 coupled tothat root port. This blocks any further traffic from the I/O devices 108through that root port.

At step 504, grant signals to each DMA channel controller are blocked.In order for a DMA request to reach the memory controller 124, anarbiter within the I/O controller 122 must provide a grant signal to theDMA engine. When the grant signals are withheld, the DMA channelcontroller is unable to send new requests through the I/O controller122. Thus, new requests will be withheld, even in the event that the DMAengine reboots before the CPU 104 is powered down after the DMA engineis reset in step 506.

At step 506, writes to the channel reset register of each DMA channelcontroller are performed. This may terminate the ongoing DMA transfersat the nearest chunk boundary (e.g., 64 bytes). Before proceeding, PCU120 may verify that the channel is in reset.

A similar flow is followed for the GbE controller. At step 508, areset_warn message is sent to the GbE controller to prepare thecontroller for a reset. At step 510, an IOSF primary grant signal to theGbE controller is blocked. This will prevent future requests from theGbE controller from being granted by the I/O controller 122, thuspreventing these requests from making forward progress. At step 512, theGbE controller is reset.

Some of the steps illustrated in FIG. 5 may be repeated, combined,modified or deleted where appropriate, and additional steps may also beadded to the flowchart. Additionally, steps may be performed in anysuitable order without departing from the scope of particularembodiments.

A design may go through various stages, from creation to simulation tofabrication. Data representing a design may represent the design in anumber of manners. First, as is useful in simulations, the hardware maybe represented using a hardware description language (HDL) or anotherfunctional description language. Additionally, a circuit level modelwith logic and/or transistor gates may be produced at some stages of thedesign process. Furthermore, most designs, at some stage, reach a levelof data representing the physical placement of various devices in thehardware model. In the case where conventional semiconductor fabricationtechniques are used, the data representing the hardware model may be thedata specifying the presence or absence of various features on differentmask layers for masks used to produce the integrated circuit. In someimplementations, such data may be stored in a database file format suchas Graphic Data System II (GDS II), Open Artwork System InterchangeStandard (OASIS), or similar format.

In some implementations, software based hardware models, and HDL andother functional description language objects can include registertransfer language (RTL) files, among other examples. Such objects can bemachine-parsable such that a design tool can accept the HDL object (ormodel), parse the HDL object for attributes of the described hardware,and determine a physical circuit and/or on-chip layout from the object.The output of the design tool can be used to manufacture the physicaldevice. For instance, a design tool can determine configurations ofvarious hardware and/or firmware elements from the HDL object, such asbus widths, registers (including sizes and types), memory blocks,physical link paths, fabric topologies, among other attributes thatwould be implemented in order to realize the system modeled in the HDLobject. Design tools can include tools for determining the topology andfabric configurations of system on chip (SoC) and other hardware device.In some instances, the HDL object can be used as the basis fordeveloping models and design files that can be used by manufacturingequipment to manufacture the described hardware. Indeed, an HDL objectitself can be provided as an input to manufacturing system software tocause the described hardware.

In any representation of the design, the data may be stored in any formof a machine readable medium. A memory or a magnetic or optical storagesuch as a disc may be the machine readable medium to store informationtransmitted via optical or electrical wave modulated or otherwisegenerated to transmit such information. When an electrical carrier waveindicating or carrying the code or design is transmitted, to the extentthat copying, buffering, or re-transmission of the electrical signal isperformed, a new copy is made. Thus, a communication provider or anetwork provider may store on a tangible, machine-readable medium, atleast temporarily, an article, such as information encoded into acarrier wave, embodying techniques of embodiments of the presentdisclosure.

A module as used herein refers to any combination of hardware, software,and/or firmware. As an example, a module includes hardware, such as amicro-controller, associated with a non-transitory medium to store codeadapted to be executed by the micro-controller. Therefore, reference toa module, in one embodiment, refers to the hardware, which isspecifically configured to recognize and/or execute the code to be heldon a non-transitory medium. Furthermore, in another embodiment, use of amodule refers to the non-transitory medium including the code, which isspecifically adapted to be executed by the microcontroller to performpredetermined operations. And as can be inferred, in yet anotherembodiment, the term module (in this example) may refer to thecombination of the microcontroller and the non-transitory medium. Oftenmodule boundaries that are illustrated as separate commonly vary andpotentially overlap. For example, a first and a second module may sharehardware, software, firmware, or a combination thereof, whilepotentially retaining some independent hardware, software, or firmware.In one embodiment, use of the term logic includes hardware, such astransistors, registers, or other hardware, such as programmable logicdevices.

Use of the phrase ‘to’ or ‘configured to,’ in one embodiment, refers toarranging, putting together, manufacturing, offering to sell, importingand/or designing an apparatus, hardware, logic, or element to perform adesignated or determined task. In this example, an apparatus or elementthereof that is not operating is still ‘configured to’ perform adesignated task if it is designed, coupled, and/or interconnected toperform said designated task. As a purely illustrative example, a logicgate may provide a 0 or a 1 during operation. But a logic gate‘configured to’ provide an enable signal to a clock does not includeevery potential logic gate that may provide a 1 or 0. Instead, the logicgate is one coupled in some manner that during operation the 1 or 0output is to enable the clock. Note once again that use of the term‘configured to’ does not require operation, but instead focus on thelatent state of an apparatus, hardware, and/or element, where in thelatent state the apparatus, hardware, and/or element is designed toperform a particular task when the apparatus, hardware, and/or elementis operating.

Furthermore, use of the phrases ‘capable of/to,’ and or ‘operable to,’in one embodiment, refers to some apparatus, logic, hardware, and/orelement designed in such a way to enable use of the apparatus, logic,hardware, and/or element in a specified manner. Note as above that useof to, capable to, or operable to, in one embodiment, refers to thelatent state of an apparatus, logic, hardware, and/or element, where theapparatus, logic, hardware, and/or element is not operating but isdesigned in such a manner to enable use of an apparatus in a specifiedmanner.

A value, as used herein, includes any known representation of a number,a state, a logical state, or a binary logical state. Often, the use oflogic levels, logic values, or logical values is also referred to as 1'sand 0's, which simply represents binary logic states. For example, a 1refers to a high logic level and 0 refers to a low logic level. In oneembodiment, a storage cell, such as a transistor or flash cell, may becapable of holding a single logical value or multiple logical values.However, other representations of values in computer systems have beenused. For example the decimal number ten may also be represented as abinary value of 118A0 and a hexadecimal letter A. Therefore, a valueincludes any representation of information capable of being held in acomputer system.

Moreover, states may be represented by values or portions of values. Asan example, a first value, such as a logical one, may represent adefault or initial state, while a second value, such as a logical zero,may represent a non-default state. In addition, the terms reset and set,in one embodiment, refer to a default and an updated value or state,respectively. For example, a default value potentially includes a highlogical value, i.e. reset, while an updated value potentially includes alow logical value, i.e. set. Note that any combination of values may beutilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code setforth above may be implemented via instructions or code stored on amachine-accessible, machine readable, computer accessible, or computerreadable medium which are executable by a processing element. Anon-transitory machine-accessible/readable medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formreadable by a machine, such as a computer or electronic system. Forexample, a non-transitory machine-accessible medium includesrandom-access memory (RAM), such as static RAM (SRAM) or dynamic RAM(DRAM); ROM; magnetic or optical storage medium; flash memory devices;electrical storage devices; optical storage devices; acoustical storagedevices; other form of storage devices for holding information receivedfrom transitory (propagated) signals (e.g., carrier waves, infraredsignals, digital signals); etc., which are to be distinguished from thenon-transitory mediums that may receive information there from.

Instructions used to program logic to perform embodiments of thedisclosure may be stored within a memory in the system, such as DRAM,cache, flash memory, or other storage. Furthermore, the instructions canbe distributed via a network or by way of other computer readable media.Thus a machine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer), but is not limited to, floppy diskettes, optical disks,Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks,Read-Only Memory (ROMs), Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), magnetic or optical cards, flashmemory, or a tangible, machine-readable storage used in the transmissionof information over the Internet via electrical, optical, acoustical orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Accordingly, the computer-readablemedium includes any type of tangible machine-readable medium suitablefor storing or transmitting electronic instructions or information in aform readable by a machine (e.g., a computer).

Various embodiments may provide an apparatus, a system, hardware- and/orsoftware-based logic, or a non-transitory machine readable medium(including information to represent structures, when manufactured, to beconfigured) to comprise a processor and a power control unit. The powercontrol unit is to, upon detection of a power loss from a primary powersource, communicate with an input/output (I/O) controller to disablerequests from I/O devices to write data to a volatile memory; requestthat all pending write requests received from the I/O devices be writtento the volatile memory; and cause the volatile memory to be placed intoa self-refresh mode after the pending write requests are written to thevolatile memory.

In at least one example, the power control unit is further to instruct amemory controller to block incoming write requests from the I/O devicesprior to the pending write requests being written to the volatilememory.

In at least one example, the power control unit is further to send anindication that the volatile memory has been placed into theself-refresh mode to logic coupled to a backup power source for thememory.

In at least one example, communicating with the I/O controller todisable requests from I/O devices comprises disabling one or more linksto the I/O devices.

In at least one example, communicating with the I/O controller todisable requests from I/O devices comprises resetting an I/O device ofthe I/O devices.

In at least one example, communicating with the I/O controller todisable requests from I/O devices comprises writing to a controlregister of a root port of the I/O controller.

In at least one example, the processor core, power control unit, and I/Ocontroller are on the same integrated circuit die.

In at least one example, communicating with the I/O controller todisable requests from I/O devices comprises instructing an arbiter ofthe I/O controller to block a grant signal to an integrated I/O device.

In at least one example, the I/O controller comprises at least onePeripheral Component Interconnect Express (PCIe) root port.

In at least one example, the I/O controller comprises at least one PCIeendpoint integrated on the same integrated circuit die as the processorcore.

Various embodiments may provide an apparatus, a system, a machinereadable storage, a machine readable medium, hardware- and/orsoftware-based logic, a method, or a non-transitory machine readablemedium (including information to represent structures, whenmanufactured, to be configured) to upon detection of a power loss from aprimary power source, communicate with an input/output (I/O) controllerto disable requests from I/O devices to write data to a volatile memory;request that all pending write requests received from the I/O devices bewritten to the volatile memory; cause the volatile memory to be placedinto a self-refresh mode after the pending write requests are written tothe volatile memory; and provide, to logic controlling the provision ofa backup power source to the volatile memory, an indication that thevolatile memory has been placed into the self-refresh mode.

In at least one example, a memory controller is instructed to blockincoming write requests from the I/O devices prior to the pending writerequests being written to the volatile memory.

In at least one example, the backup power source is provided to thevolatile memory after the volatile memory is placed into theself-refresh mode.

In at least one example, communicating with the I/O controller todisable requests from I/O devices to write data to the volatile memorycomprises disabling one or more links to the one or more I/O devices.

In at least one example, communicating with the I/O controller todisable requests from I/O devices to write data to the volatile memorycomprises writing to a control register of a root port of the I/Ocontroller.

Various embodiments may provide an apparatus, a system, hardware- and/orsoftware-based logic, or a non-transitory machine readable medium(including information to represent structures, when manufactured, to beconfigured) to comprise a processor core, a volatile memory, a memorycontroller to be coupled to the volatile memory, an input/output (I/O)controller to be coupled to the memory controller, a display, and apower control unit. The power control unit is to, upon detection of apower loss from a primary power source, communicate with the I/Ocontroller to disable requests from I/O devices to write data to thevolatile memory; request that all pending write requests received fromthe I/O devices be written to the volatile memory; and cause thevolatile memory to be placed into a self-refresh mode after the pendingwrite requests are written to the volatile memory.

In at least one example, the power control unit is further to instructthe memory controller to block incoming write requests prior tocompleting pending write requests stored by the memory controller.

In at least one example, a battery backup unit is to provide a backuppower source to the volatile memory after the volatile memory is placedinto the self-refresh mode.

In at least one example, communicating with the I/O controller todisable requests from the I/O devices to write data to the volatilememory comprises disabling one or more links to the I/O devices.

In at least one example, communicating with the I/O controller todisable requests from the I/O devices to write data to the volatilememory comprises writing to a control register of a root port of the I/Ocontroller.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present disclosure. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

In the foregoing specification, a detailed description has been givenwith reference to specific exemplary embodiments. It will, however, beevident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the disclosure asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense. Furthermore, the foregoing use of embodiment andother exemplarily language does not necessarily refer to the sameembodiment or the same example, but may refer to different and distinctembodiments, as well as potentially the same embodiment.

1.-20. (canceled)
 21. An apparatus comprising: a processor core; and apower control unit to, in response to a detection of a power loss from aprimary power source: instruct an input/output (I/O) controller todisable requests from I/O devices to write data to a system memory;instruct a memory controller to block incoming write requests; and afterinstructing the I/O controller to disable requests from the I/O devicesand instructing the memory controller to block incoming write requestfrom the I/O devices, send a request to the memory controller for allpending write requests received from the I/O devices to be written tothe system memory.
 22. The apparatus of claim 21, the power control unitfurther to cause the system memory to be placed into a self-refresh modeafter the pending write requests are written to the system memory. 23.The apparatus of claim 22, wherein the power control unit is further tosend an indication that the system memory has been placed into theself-refresh mode to logic coupled to a backup power source for thesystem memory.
 24. The apparatus of claim 21, wherein instructing theI/O controller to disable requests from I/O devices comprises disablingone or more links to the I/O devices.
 25. The apparatus of claim 21,wherein instructing the I/O controller to disable requests from I/Odevices comprises resetting an I/O device of the I/O devices.
 26. Theapparatus of claim 21, wherein instructing the I/O controller to disablerequests from I/O devices comprises writing to a control register of aroot port of the I/O controller.
 27. The apparatus of claim 21, whereininstructing the I/O controller to disable requests from I/O devicescomprises instructing an arbiter of the I/O controller to block a grantsignal to an integrated I/O device.
 28. The apparatus of claim 21,wherein the I/O controller comprises at least one Peripheral ComponentInterconnect Express (PCIe) root port.
 29. The apparatus of claim 21,wherein the I/O controller comprises at least one PCIe endpointintegrated on the same integrated circuit die as the processor core. 30.The apparatus of claim 21, wherein the power control unit is to instructthe memory controller to block the incoming write requests in responseto receiving an indication from the I/O controller that the I/Ocontroller has sent pending write requests to the memory controller. 31.The apparatus of claim 21, wherein the power control unit is to send therequest to the memory controller for all pending requests received fromthe I/O devices to be written to the system memory in response toreceiving an indication from the memory controller that the memorycontroller is to block incoming write requests.
 32. The apparatus ofclaim 21, the power control unit further to send a flush buffer requestto the I/O controller to flush pending requests to the memory controllerin response to receiving an indication from the I/O controller that theI/O controller is to disable requests from I/O devices to write data toa system memory.
 33. The apparatus of claim 21, further comprising thesystem memory.
 34. The apparatus of claim 33, further comprising adisplay or a network adapter coupled to the processor core.
 35. A methodcomprising: in response to a detection of a power loss from a primarypower source: instructing an input/output (I/O) controller to disablerequests from I/O devices to write data to a system memory; instructinga memory controller to block incoming write requests; and afterinstructing the I/O controller to disable requests from the I/O devicesand instructing the memory controller to block incoming write requestfrom the I/O devices, sending a request to the memory controller for allpending write requests received from the I/O devices to be written tothe system memory.
 36. The method of claim 35, further comprisingcausing the system memory to be placed into a self-refresh mode afterthe pending write requests are written to the system memory.
 37. Themethod of claim 35, further comprising sending the request to the memorycontroller for all pending requests received from the I/O devices to bewritten to the system memory in response to receiving an indication fromthe memory controller that the memory controller is to block incomingwrite requests.
 38. A system comprising: a processor core; means fordetecting a power loss from a primary power source; means forinstructing an input/output (I/O) controller to disable requests fromI/O devices to write data to a system memory; means for instructing amemory controller to block incoming write requests; and means forsending a request to the memory controller for all pending writerequests received from the I/O devices to be written to the systemmemory after instructing the I/O controller to disable requests from theI/O devices and instructing the memory controller to block incomingwrite request from the I/O devices.
 39. The system of claim 38, furthercomprising means for causing the system memory to be placed into aself-refresh mode after the pending write requests are written to thesystem memory.
 40. The system of claim 39, further comprising means forproviding a backup power source to the system memory after the systemmemory is placed into the self-refresh mode.